FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2

4.2.13.357 HL7 Version 2 Table 0357

Vocabulary Work Group Maturity Level: N/AExternalUse Context: Any

This is a table defined as part of HL7 v2 . Related FHIR content: v2 Message Error Condition Codes.

Summary

Name:v2 Message Error Condition Codes
Definition:FHIR Value set/code system definition for HL7 v2 table 0357 ( Message Error Condition Codes)
Code System URL:http://hl7.org/fhir/v2/0357
Value Set URL:http://hl7.org/fhir/ValueSet/v2-0357
OID:??
CodeSystem ResourceXML / JSON
ValueSet ResourceXML / JSON

This value set is used in the following places:

Message Error Condition Codes

CodeDescriptionDeutsch (German)Nederlands (Dutch)CommentVersion
0 Message acceptedNachricht akzeptiertBericht geaccepteerdSuccess. Optional, as the AA conveys success. Used for systems that must always return a status code.added v2.3.1
100 Segment sequence errorFehler in der SegmentreihenfolgeFout in segmentvolgordeError: The message segments were not in the proper order, or required segments are missing.added v2.3.1
101 Required field missingerforderliches Feld leerVerplicht veld ontbreektError: A required field is missing from a segmentadded v2.3.1
102 Data type errorDatentypfehlerFout in datatypeError: The field contained data of the wrong data type, e.g. an NM field contained "FOO".added v2.3.1
103 Table value not foundfehlender Eintrag in der TabelleTabelwaarde niet gevondenError: A field of data type ID or IS was compared against the corresponding table, and no match was found.added v2.3.1
104 Value too longWaarde te langError: a value exceeded the normative length, or the length that the application is able to safely handle.added v2.7
200 Unsupported message typeNachrichtentyp wird nicht unterstütztNiet-ondersteund berichttypeRejection: The Message Type is not supported.added v2.3.1
201 Unsupported event codeEreignis wird nicht unterstütztNiet-ondersteunde eventcodeRejection: The Event Code is not supported.added v2.3.1
202 Unsupported processing idProcessing-ID wird nicht unterstütztNiet-ondersteunde processing idRejection: The Processing ID is not supported.added v2.3.1
203 Unsupported version idVersion wird nicht unterstütztNiet-ondersteunde versieRejection: The Version ID is not supported.added v2.3.1
204 Unknown key identifierSchlüsselwert nicht gefundenOnbekende sleutel-identificatieRejection: The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient.added v2.3.1
205 Duplicate key identifierdoppelter SchlüsselwertDuplicaat sleutel-identificatieRejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).added v2.3.1
206 Application record lockedDatensatz durch Applikation gesperrtApplicatie record vergrendeldRejection: The transaction could not be performed at the application storage level, e.g. database locked.added v2.3.1
207 Application internal errorapplikationsinterner FehlerInterne applicatiefoutRejection: A catchall for internal errors not explicitly covered by other codes.added v2.3.1